Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

TPO 2026

reference: 801-tree-1
name: TPO 2026
tree-preservation-order: undefined
801-tpo-1
uprn
address-text
point: POINT (-0.973622 50.786248)
geometry: MULTIPOLYGON (((-0.973566 50.786242,-0.973568 50.786253,-0.973576 50.786263,-0.973588 50.786271,-0.973604 50.786276,-0.973622 50.786278,-0.973639 50.786277,-0.973655 50.786272,-0.973668 50.786264,-0.973676 50.786254,-0.973679 50.786243,-0.973677 50.786232,-0.973669 50.786222,-0.973656 50.786214,-0.973641 50.786208,-0.973623 50.786206,-0.973606 50.786208,-0.973590 50.786213,-0.973577 50.786221,-0.973569 50.786231,-0.973566 50.786242)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL